<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
    <link rel="icon" href="../images/logo/logo.png" type="image/x-icon">
    <link rel="shortcut icon" href="../images/logo/logo.png"
          type="image/x-icon">
    <title>浏阳德塔软件开发有限公司 女娲计划</title>
</head>
<body style="Max-width: 700px; text-align:center; margin:auto;">
<div style="text-align:left; Max-width: 680px; margin-left:15px;">
    <a href="../">上一页</a>
    <br/>
    <br/>
    <br/>第七章 类人DNA与神经元基于催化算子映射编码方式
    <br/>The Initons Catalytic Reflection Between Humanoid DNA and Nero
    Cell
    <br/>类人 DNA 与 神经元基于催化算子映射编码方式
    <br/>Yaoguang Luo, Rongwu Luo
    <br/>罗瑶光, 罗荣武
    <br/>Keywords
    <br/>VPCS, AOPM, IDUC, Nero, Artificial, Decoder, Medical, Paralling,
    Computing,
    <br/>Humanoid, ETL, Parser, Data Mining
    <br/>关键词
    <br/>VPCS 架构 AOPM 逻辑 IDUC 编码 神经元 人工 解码 医学 并行计算 类人仿生 ETL 数据挖掘
    爬取

    <br/>VPCS Backend Theory And Its Application
    <br/>Mr. Yaoguang. Luo

    <br/>Outline: due to the development of the software acquisition and
    definition in what we use the code theory always in messy and
    unforeseeable status. A new method of the coding style like VPCS that
    will show in this topic paper, feel free to resonate with my
    imagination of the portrait—VPCS (Vision, Process, Controller, Sets)
    theory, fun yet? Not only this paper will gazer a big point how we show
    the constructions of the VPCS, you guys also sure to get lots of
    idyllic landscapes of the coding sections. While you got lots of the
    illness codes at the so messy fungus projects, I guess at this paper
    out where you are finding anxiously. Let’s catch more opportunity about
    how does the VPCS working, executing and scheduling in our software
    project and make the software fast, fast and safe! lets go, So the key
    words as below:
    <br/>
    大纲:由于软件的发展, 在获取和定义方面我们所使用的代码理论总是处于混乱和不可预见的状态.
    一种新的编码风格的方法, 如VPCS, 将在这篇专题论文中展示, 请随意与我想象的肖像- VPCS
    (视觉, 操作过程, 控制处理器, 静态集)理论产生共鸣, 有趣吗?不仅这篇论文将关注一个大的点
    , 我们如何显示构建的vpc, 你也一定会得到许多田园风景般的编码部分. 当你在如此混乱的细琐
    项目中得到许多病垢代码时, 我猜在这篇论文中你会感到不安. 让我们抓住更多的机会, 如何工作
    的vpc, 执行和计划, 在我们的软件项目, 使软件快速, 快速和安全! Let’s go, 所以关键字如下:
    <br/>Quantum Sets, Concurrent Consumer, Vision, Scheduler, Threads, Surf.
    <br/>Introductions
    <br/>Let see the verbal keys, the first time you …, okay, get any
    sense? Sure, this paper is not talking about the human careers, truly
    about SOFTWARER, as a human, if you got my points, yes, cool! Make any
    sense? Let’s see the landscape as below figure 1-1.
    <br/>让我们看看语言键, 第一次你…, 明白了吗?当然, 这篇文章并不是在讨论人类的酒店职业生涯,
    而是真正地讨论作为一个类人的软件生命存在, 如果你明白我的观点, 是的, 很酷!任何意义?让我们看看如下图
    1-1 所示的景观.
    <img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_6.jpg"
         alt="浏阳德塔软件开发有限公司,罗瑶光"/>
    <br/>Figure 1-1 VPCS STAR MODE
    <br/>
    From the ordinary software development architecture, always like
    a factory mode, for instance, controller, transaction delegate, web
    service, job bean, data DAO, like that of traditional backend or
    front-end coding style, but, compare now the seamless client’s services
    system, those mode more and more not suitable for us for the project
    application, at least in the light level, multitasks, satellite boots
    projects system, if we choice the factory mode, you will feel so heavy.
    But the big conflict problem is where the factory mode was used in all
    and all bazaar companies. Even more CTOs that I met before often
    complaining about the reference room likes that “we need one server for
    database system, one more for cache system, one more for front end, one
    more, for backend, one more….” after that what do you think? My lord…
    <br/>
    从普通的软件开发架构来看, 总是像一个工厂模型, 例如, 控制器, 事务委托, web 服务,
    工作 bean 数据通道, 像传统的后端或前端编码风格, 但是, 对比现在, 无缝的客户服务系统,
    这些模型越来越不适合我们项目的应用程序中, 至少在轻微水平级别, 多线程事务的同时, 卫星
    集群般部署的项目系统, 如果我们选择工厂模型, 你会觉得很沉重. 但最大的冲突问题是, 工厂
    模式被用于所有的集市公司. 更多的 cto 经常抱怨资料室, 比如“我们需要一个数据库服务器,
    一个缓存服务器, 一个前端服务器, 一个后端服务器, 一个……”, “那之后你觉得怎么样?”我的主…
    <br/>
    Finding a new method of how to integrate the sets about the
    micro satellites service in the same sever, and make them small,
    lightly and faster for the commercial service, now become a fatal
    topic. Which can be a pretty warm-up for where I make an explanation
    for VPCS. The VPCS mode, only includes four aspects. Vision, Process,
    Controller, Sets, and those factors makes an interaction in the sleeper
    containers. Let talk about the definition of the sleepers. From the
    software engineering domain, the sleepers are more like an identified
    thread person. Who can make a lot of fantasy-dreams in a Hall, what
    means a dream? Dream is a requirement what the consumer really needs to
    finished. But here the dream can be separated out more tasks, those
    tasks will register the ID in the Pillow, so that the sleeper hugs the
    pillow then goes into the hall and make a dream. Got an idea? Cool. So,
    what does the sleeper does in a hall? The answer is to make all kinds
    of the dream. For example, if we want to build the web service to get
    rest call, and return the JSON feedbacks, we only need to do like the
    way: Firth, build rest call path in the controller; Second: register
    the call requirements as a dream; Third, build the sets of the dream in
    the pillow, fourth hire a sleeper to hug this pillow, and go to the
    hall to make a dream process. At last, but least: return the dream
    goods. Any sense? Cool! For this unique instance, you will know that
    the sleeper was more like a socket, and the hall more like a thread
    pool, the pillows like the single visionary instance, and the sets like
    a visionary storage, the controller and the process those two sections
    is a common way of the factory mode. The steps landscape of the sleeper
    who makes a dream as bellow figure 1-2.
    <br/>
    如何在同一服务器上集成微卫星蜂群服务设备, 使其小型化、轻量化、快速化, 成为当前重要的课题.
    这对于我解释 vpc 来说是一个很好的热身. VPCS 模型, 只包括四个方面. 视觉、过程、控制器、
    设置以及这些因素在轨枕容器中进行交互. 让我们来谈谈梦想家的定义. 从软件工程领域来看,
    “梦想家休眠者”更像是一个已确定的线程 人员. 谁能在大厅里做很多幻想的梦, 梦是什么意思?
    梦想是消费者真正需要完成的一项要求. 但是在这里, 梦可以被分离出更多的任务, 这些任务会在
    枕头上登记 ID, 所以睡觉的人拥抱枕头, 然后走进大厅做一个梦. 有一个主意吗? 酷. 那么卧铺
    在大厅里做什么呢? 答案是做各种各样的梦. 例如, 如果我们想要构建 web 服务来获取 rest
    调用, 并返回 JSON 反馈, 我们只需要像这样做: 首先, 在控制器中构建 rest 调用路径;
    第二:
    把呼叫要求登记为一个梦; 第三, 在枕头上搭建梦境的布景, 第四, 雇一个睡觉的人来抱这个枕头,
    然后去大厅做一个梦的过程. 最后, 但最重要的是:把梦想实现的结果输出. 任何意义? 太酷了!
    对于这个独特的实例, 您将知道睡眠更像是一个套接字, 和大厅里更像是一个线程池, 枕头像单视觉
    实例, 像是和集存储、控制器和过程这两个部分工厂的模型是一种常见的方式.
    做梦的人的台阶景观如图 1-2 所示.
    <img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_7.jpg"
         alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-2 VPCS BACKEND MODE
    <br/>
    Focus on this landscape, mostly different to the MVC: Mode View
    Controller, MVP: Mode View Presenter or other architectures we know
    before. but is very easy to understand after you read for a while. Too
    simple. Sleeper makes dreams come true, hall container sleepers, skivvy
    make up the hall, pillow clear and wake up the sleepers who often lost
    in finding the way in the dream. Got fun here, but I would hear more
    argue voice DETAils of my VPCS, desktop App once said: VPCS is good in
    the concurrent WEB project, but not suitable for the desktop
    applications. Ok, follow this question, let make a new landscape based
    on desktop application as below figure 1-3.
    <br/>
    专注于这个景观, 主要不同于 MVC: Mode View Controller, MVP: Mode View
    Presenter 或我们之前知道的其他架构. 但是读一段时间后就很容易理解了. 太简单了.
    睡眠者使梦想成真, 大厅集装箱睡眠者, skivvy 使大厅, 枕头清楚, 唤醒经常在梦中
    迷路的睡眠者. 在这里得到了乐趣, 但我将听到更多的争论声音细节关于我的 vpc 桌面应用,
    曾经有人说:vpc 是好的并行 WEB 项目, 但不适合桌面应用. 好的, 按照这个问题,
    让我们创建一个新的基于桌面应用程序的横屏, 如下图
    1-3 所示.<img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_8.jpg"
                  alt="浏阳德塔软件开发有限公司,罗瑶光"/>
    <br/>Figure 1-3 VPCS WORK WITH FRONTEND
    <br/>From this picture, we know all of the software can be fast and
    safe while using VPCS, because It is already separated out the big
    system into backend and frontend two parts. And VPCS keeps safe and
    fast in the backend section. Compare to the MVC, VPCS will get more
    cautious and DETAils, and compare to MVP, VPCS also will get more safe
    and high efficiency. Those factors are why I will make inauguration
    here. In the common software engineering cycle life times, scientist
    used to build front end and backend for all kinds of the software
    applications, because it is easy to control. Why? Frontend only spend
    time to make design, and Backend for the data operations. Using VPCS
    system, we don’t care about what they do for the front end, we only fit
    about what they want. Alignment that gets a blame and fix, then return
    OK, the restful service developer makes a voice that http functions are
    concurrent functions. At here, VPCS will say: concurrent functions are
    safe functions. We guess in the future REST-VPCS will be used in
    multiple WEB service. Especially in the high speed, efficiency, micro
    web systems with high level security for example medicine, DNA, cloud
    server, electronic police system and ecommerce systems etc.
    <br/>从这个图中, 我们知道所有的软件在使用 vpc 时都是快速和安全的, 因为它已经把
    大系统分成后端和前端两部分. VPCS 在后端部分保持安全和快速. 与 MVC 相比, VPCS 会
    更加谨慎和细致, 与 MVP 相比, VPCS 也会更加安全高效. 这些因素就是我在这里就职的原因.
    在常见的软件工程周期生命周期中, 科学家常常为各种软件应用程序构建前端和后端, 因为它易于
    控制. 为什么? 前端只花时间做设计, 后端只花时间做数据操作. 使用 vpc 系统, 我们不关心
    他们为前端做什么, 我们只适合他们想要的. 得到责备和修正, 然后返回 OK, restful
    服务开发人员发出声音说 http 函数是并发函数. 在这里, vpc 会说: 并发函数是安全函数.
    我们猜测将来 rest - vpc 将被用于多个 WEB 服务中. 特别是高速、高效、高安全级别的微 web
    系统, 如医药、DNA、云服务器、电子警察系统、电子商务系统等. 最近养疗经引擎也开始基于
    vpcs 进行布局. 其子系统已全部采用 vpcs 结构.
    <img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_9.jpg"
         alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-4 VPCS FOR DATABASE SYSTEM

    <br/>As the figure 1-4, a new method of the Database system designing
    shows us VPCS is a pretty way for the modern data information
    management system. Definitely used in the Deta Database system. For
    this instance, do we get a view that the controller section of the
    factory mode becomes thin yet? Controller only works for the hands
    transactions, for example that the controller gets an input requirement
    such as select SQL, then immediately call the hall keeper to register
    this SQL and hire new sleepers to make a result. Because of the VPCS.
    Once it happened any exceptions, will very easy to awake sleeper and
    let them get theirs working papers out, finally call skivvy to fork the
    sets to the fresh sleeper. This method mostly be like a Count Down
    Latch mode, once the sleeper gets the dreams come true, then told the
    hall keeper for the feedback, hall keeper will make a type procession
    to return after everything goes well, this method mostly be like a
    Cyclic Barrier mode.
    <br/>如图 1-4 所示, 一种新的数据库系统设计方法向我们展示了 VPCS 是现代数据信息管理系统的一种很好的方式.
    明确用于
    Deta 数据库系统. 对于这个实例, 我们是否得到了工厂模型的控制器部分变薄的视图?
    控制器仅适用于hands 事务, 例如,
    控制器获得一个输入需求(如 select SQL), 然后立即调用大厅管理员注册这个 SQL
    并雇佣新的休眠人员来生成结果. 因为 vpc.
    一旦发生任何异常, 会很容易叫醒睡眠者, 让他们拿出自己的工作底稿, 最后叫 skivvy
    把餐具叉给新的睡眠者.
    这种方法大多类似于一个倒计时锁存模型, 一旦睡眠者的梦境实现, 然后告知大厅管理员进行反馈,
    一切顺利后,
    大厅管理员会做出一个类型的队列返回, 这种方法大多类似于循环障碍模型.

    <br/>
    <br/>Questions
    <br/>How does skivvy doing? please see the figure 1-5 the hall
    building needs a singler instance like a home keeper but here is a hall
    keeper, any else, this person is very important for keeping the VPCS
    safe, because all of the skivvies will be managed by him. You will see,
    the memory check, JVM garbage collection, disk cleaning, thread status
    management, deadlock alarm, security protocol all and all in one at
    here. Mostly like a static class in the VPCS system. If we need to know
    every thing about skivvy’s work status, ok just call the hall keeper.
    <br/>skivvy 做了些什么事务? 请见图 1-5, 大厅建筑需要一个像管家一样的单例, 但是这里有一个管家,
    其他的,
    这个人对于保持 VPCS 的安全非常重要, 因为所有的 skivvies 都将由他管理. 您将在这里看到,
    内存检查、JVM
    垃圾收集、磁盘清理、线程状态管理、死锁警报、安全协议, 所有这些都集于一身. 大部分类似于
    VPCS 系统中的静态类. 如果我们需要知道
    skivvy 的工作情况, 可以打电话给大堂管理员.

    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_10.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-5 VPCS KERNEL

    <br/>How does sleeper do? Make a dream? Cool, you shoot! in the VPCS
    system, it doesn’t have the definition of the process, everything likes
    subsets. Immutable or unlined, hall keeper get request from visionary
    and hire the sleeper, who is likes a thread, get requirement, add those
    sets in pillow, hugs pillow then go to hall to make a dream, after that
    then return the callback to hall keeper what they did. Fun yet?
    <br/>睡觉的人怎么样? 做一个梦吗? 酷, 你正中目的! 在 VPCS 系统中, 它没有进程的定义,
    一切都像是子集.
    不可变的或无线条的, 厅管得到梦想者的请求, 雇佣睡眠者, 谁是线程, 得到要求, 添加那些套在枕头,
    拥抱枕头然后 去厅做一个梦,
    然后返回回厅管他们做了什么. 有趣吗?

    <br/>What does the sets mean? Sets, is a format of the data were
    appearing in the VPCS system. For the static prototype, it used like a
    concurrent hash table, and list which can be copy base on writing
    format, the single instance, it always runs in the static function or
    be liking an interface implementation because need safe at the same
    time, so that compare to the factory mode, it is too simple and without
    annotation. Everything becomes easy in this environment.
    <br/>这些集合是什么意思? 是出现在 VPCS 系统中的数据的一种格式. 静态原型, 它像一个并发的哈希表,
    使用这些列表,
    可以复制基本写作格式, 单一实例, 它总是运行在静态函数或像是一个接口实现, 因为需要安全的同时,
    与工厂模型相比, 它太简单, 没有注释.
    在这种环境下, 一切都变得容易了.

    <br/>The one more question is that so many peoples asked me what does
    the sequence diagram of the VPCS, because they really want to know why
    VPCS is faster and safer. Ok, please see the figure 1-6, the answer is
    absolutely, VPCS main components of the time sequence only contains
    five aspects. Almost similar like the hotel management. Certainly, we
    are talking about VPCS software, not for guesthouse. You will see that
    the rest call only makes the interactions with the hall keeper. And
    hall keeper got two jobs, one for waiting the fresh sleeper and one
    more for giving task to skivvy. The sleeper only hugs the relate pillow
    and make the dreams come true. Fun yet? Cool. VPCS only take cares
    about how does the sleeper’s imagination and skivvy’s working status.
    If is the pillow broken? Make new pillow, got lazy sleeper? Get out his
    working papers, got a cheat skivvy? Fix of fire him, the real source of
    the java version project for the VPCS only 30kb, we will find more
    sources or documents from the reference links at the end.
    <br/>还有一个问题是, 很多人问我 vpc 的序列图是什么, 因为他们真的想知道为什么 vpc
    更快、更安全. 好的, 请看图
    1-6, 答案是绝对的, VPCS 主要组件的时间序列只包含五个方面. 和酒店管理差不多. 当然,
    我们说的是 vpc 软件,
    而不是宾馆用的. 您将看到 rest 调用只与大厅管理员进行交互. 厅长有两份工作, 一份是等新来的人,
    另一份是给佣人分派任务.
    睡觉的人只会抱着枕边的枕头, 让美梦成真. 有趣吗? 酷. VPCS 只关心睡眠者的想象力和skivvy
    的工作状态. 如果枕头被打破了?
    做新枕头, 遇到睡懒觉的梦想家吗? 把他的工作文件拿出来, 有个服务骗子吗? 修复或者炒了他,
    真正的 java 版本项目的源代码为 VPCS
    只有 30kb, 我们将在后面的参考链接中找到更多的源代码或文档.

    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_11.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6 VPCS Sequence Diagram

    <br/>I always be asked by the colleagues that once said: how does the
    hall build? I answered them, such like the hospital, no one cares about
    the address of hospital, because they just call the cell phone number
    when will get a directly feedback. This is why I need a hall keeper
    role in the gate way. For the instance about figure 1. 6. 1, this
    sample is a true demo in the real world for the WEB rest service. Its
    very important to create a player role such like hall keeper. What
    would like about author’s theory? Because of the maintenance. Because
    of whom, the software build team are very easy to make a maintenance
    web portal, all of the system current status will be solved on this
    html page by DEVOPS.
    <br/>我总是被问道 VPCS 中的 大堂经理用来干什么, 我回答说 正如一个医院, 没人关心医院的地址,
    因为他们拨打 120
    救护车就来了. 大堂经理就像这个接电话的. 后端接口请求同样, 没有哪个事务逻辑需要知道怎么被执行,
    因为大堂经理按照索引规范已经登记好了.
    这种登记方式非常容易被开发运维人员维护操作.


    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_12.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-1 The Interaction Between Rest Call and Hall Keeper

    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_13.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-2 The Interaction Between Hall Keeper and Sleepers

    <br/>Many of these software developers also asked me how and why we
    fork out the LAZZY sleepers excluding their sets. Arthur answered
    because of the pillows. When the sleepers be hired from the hall
    keeper, they will get an independently pillows such like static
    functions. So that sleeper only has their own indentify attributes and
    unique information as the singe instance class. Once they got theirs
    working paper, the pillows they used will be arranged to the new fresh
    sleeper, this theory keeps safe, quality and quantity. Like figure 1.
    6. 2. 1 VPCS kernel.
    <br/>很多软件开发者同样会问我 如果删除掉一些睡懒觉的线程, 他们的枕头怎么处理? 这就是
    vpcs 的闪光点, 因为枕头是 id
    标识的静态数据, 所以, 是可以重用的. 新的梦想家可以从这些枕头里提取有用的数据碎片.
    (当然这里是软件不是酒店,
    酒店的枕头是要高温清晰消毒的^-^)

    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_14.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-2-1 VPCS kernel

    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_15.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-3 The Interaction Between Sleepers and skivvy

    <br/>Many times, I got questions about the DEVOPS, they really worry
    about VPCS if suitable for their project system maintenance? The answer
    is absolutely, as the Mr. Ray 274138705@qq. com once said: we are
    DEVOPS, at least we need three important keys in our environment
    assignments: implementation capacity, transparency and maneuverability.
    How does the VPCS supports us for daily works? Because of Hall Keeper
    and skivvy, as figure 1-6-3 and 1-6-4. DEVOPS will get all of this
    transparency information about project from hall keeper under the
    encryption and security issues. Also, hall keeper will directly get the
    rule for DEVOPS by rest calls, then makes to commend to skivvy. All of
    the information and record logger will be cached by hall keeper, that
    keeps controllability. The html control page will make an interaction
    between hall keeper and DEVEOPS, which keeps safe, implementation
    capacity, transparency and maneuverability. This is my true answer.
    <br/>很多时候, 我被一些运维问道, 采用了vpcs 架构怎么进行系统维护? 答案是很明确的, ray
    先生曾问我
    作为运维他们往往纠结于 耦合度, 透明度和可维护性 vpcs 具体是怎么体现的? 我的回答是
    大堂经理与服务员的命令落实,
    这些落实情况可以进行完整的可观测的日志记录, 内存状态, 中间属性标识.,


    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_16.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-4 The Interaction Between Skivvy and Hall Keeper

    <br/>Recently Mr. Yang 1291244774@qq. com who asked me about VPCS of
    IOS desktop APP, where and how to avoid the data leakage risks. Because
    he really worries about the separation between controller and process.
    Following this topic, my answer that the key is the separation between
    pillows and sleepers. Due to the pillows all have their own unique ID,
    skivvy will easily arrange the pillow to new sleeper after the original
    sleeper who made problems. Make unique ID and arrangement by ID, is the
    key method. Also, for the rest call service, the asymmetrically
    irreversible combination encryption is one of the best solutions to the
    data leakage controller. VPCS seems so smart.
    <br/>最近 yang 问我 vpcs 能用在 IOS 中么? 因为它担心 pc 分离 有可能 导致 数据的溢出,
    我的回答是绝对的安全, 因为每一个线程都进行了唯一的公有标识, 连静态属性, 单例属性都有明确的属性表示,
    这个标识能在内存中时时刻刻着找到它的状态. 另外 rest 的异步消息握手同样能够进行精准的维护.


    <br/><img class="banner_img" style="width: 100%" src="../images/5_7108/7/7_17.jpg"
              alt="浏阳德塔软件开发有限公司,罗瑶光"/>

    <br/>Figure 1-6-5 The Interaction Between Sleepers and Pillows

    <br/>
</div>
</body>